Skip to content

fix: use ubuntu-latest as ci runner #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
UlisesGascon merged 1 commit into from
Jun 5, 2025
Merged

fix: use ubuntu-latest as ci runner #32

UlisesGascon merged 1 commit into from
Jun 5, 2025

Conversation

@UlisesGascon
Copy link
Member

@UlisesGascon UlisesGascon commented May 18, 2025

No description provided.

@UlisesGascon UlisesGascon requested a review from blakeembrey May 18, 2025 16:41
@UlisesGascon
Copy link
Member Author

UlisesGascon commented May 18, 2025

This will require some work. I am not working on this now, so help is more than welcome :)

So far seems like the signatures for [email protected] are not available (ref)

Get:37 http://us.archive.ubuntu.com/ubuntu bionic InRelease [242 kB]
Err:8 http://security.ubuntu.com/ubuntu bionic-security InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3B4FE6ACC0B21F32
Err:37 http://us.archive.ubuntu.com/ubuntu bionic InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3B4FE6ACC0B21F32
Reading package lists...
W: GPG error: http://security.ubuntu.com/ubuntu bionic-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3B4FE6ACC0B21F32
E: The repository 'http://security.ubuntu.com/ubuntu bionic-security InRelease' is not signed.
W: GPG error: http://us.archive.ubuntu.com/ubuntu bionic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3B4FE6ACC0B21F32
E: The repository 'http://us.archive.ubuntu.com/ubuntu bionic InRelease' is not signed.
Error: Process completed with exit code 100.

@bjohansebas
Copy link
Member

bjohansebas commented May 18, 2025

same here jshttp/forwarded#18 (comment)

@UlisesGascon UlisesGascon self-assigned this Jun 5, 2025
@UlisesGascon
Copy link
Member Author

UlisesGascon commented Jun 5, 2025

We can solve the [email protected] as an independent issue

@UlisesGascon UlisesGascon merged commit a3fa6d8 into master Jun 5, 2025
3 of 52 checks passed
@UlisesGascon UlisesGascon deleted the fix-ci branch June 5, 2025 13:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@blakeembrey blakeembrey Awaiting requested review from blakeembrey

Assignees

@UlisesGascon UlisesGascon

Labels

fast track

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@UlisesGascon @bjohansebas